Method and apparatus for facilitating payment via mobile networks

ABSTRACT

A method and apparatus for facilitating payments for transactions, via mobile devices and mobile telecommunications networks, is disclosed. In an embodiment, a product provider is provided with a code, such as a QRcode, which contains or references payment details for purchase of the product. A mobile user of the application scans the code and is connected to their internet banking application. The payment details are transferred to the internet banking application and the mobile user confirms that the transaction should proceed. Payment is made without any secure details being provided to the product provider.

FIELD OF THE INVENTION

The present invention relates to a method and apparatus for facilitatingpayments for transactions via telecommunications networks and,particularly, but not exclusively, to a method and apparatus forfacilitating payments via mobile devices and mobile telecommunicationsnetworks.

BACKGROUND OF THE INVENTION

It is known to “shop” over the Internet. A large volume of products(goods and services) are transacted via the Internet.

Security of information transmitted over networks such as the Internetis an important issue. On-line release of private information, such ascredit card numbers, debit card numbers or any other transaction relatedprivate information, is a major security issue. The misappropriation ofsuch private information to conduct fraudulent transactions is wellknown and a major problem.

A number of solutions have been proposed to deal with this problem. Theapplicant's own earlier patent application, PCT/AU2004/000846, proposesA System and Method for Facilitating On-Line Payment, where a customerdoes not have to provide private information, such as credit carddetails, over the Internet to merchants. Instead, the applicant'searlier system provides an interface which automatically connects thecustomer's computer to the customer's own financial institution bankingapplication (e.g. Internet banking application). A customer then paysfor the transaction via the financial institution application. Themerchant (eg merchant providing on-line web pages for sale of product)is provided with a receipt. No private transaction information, such ascredit card details, needs to be provided to the merchant.

The use of mobile devices for communications, eg mobile telephones (alsoknown as “cellular” telephones) is well known. As these devices andtheir communications networks have become more sophisticated, they havefound use in many other applications apart from voice communications.One of the applications that they have found use in is in payment fortransactions, utilising the mobile device. The same issues of securityregarding private payment information apply with mobile devices as theydo to on-line transactions using other types of communications devices,such as desktop computers.

There is a need for improvements in security and ease of use relating topayment transactions carried out via mobile devices.

SUMMARY OF THE INVENTION

In accordance with a first aspect, the present invention provides acustomer apparatus for facilitating payment transactions between acustomer and a product provider, the customer apparatus comprising areader arranged to read a product provider artefact storing transactiondata about the transaction, to obtain the transaction data, and atransaction process arranged to connect over a communication network toa financial institution application of a financial institutionadministering a customer account of the customer, to provide thetransaction data to the financial institution application, so that thefinancial institution can make payment for the transaction from thecustomer account.

In an embodiment, the transaction process enables provision from thecustomer apparatus of a security device to the financial institutionapplication. The security device may enable the financial institutionapplication to proceed with the transaction. In an embodiment, thesecurity device may be a password, a biometric, or any other securitydevice.

In an embodiment, the customer apparatus is a mobile device. It may be amobile telephone, PDA, tablet computer, or any other mobile device whichcan transmit and receive information over a mobile telecommunicationsnetwork or other wireless or wired network.

In an embodiment, the mobile device comprises a transceiver fortransmitting and receiving information over a mobile communicationsnetwork. Other embodiments may utilise any other type of wireless orwired network. It also comprises a processor for processing data andapplications' (eg software in the form of a computer program) and amemory for storing data and programs. Such devices are well known.

In an embodiment, the reader comprises a software module which isarranged to read the transaction data from the product providerartefact. The product provider artefact may be a visible code which ispresented by a product provider. The code may be QRcode, barcode, or anyother type of visible code. In this embodiment, the reader is arrangedto read the code via a hardware interface of the customer apparatus,such as a camera or other mechanism arranged to obtain images.

In another embodiment, the product provider artefact may comprise amemory and a transmitter for transmitting data from the memory, eg viawireless transmission. The artefact may comprise an RFID device, forexample, or other type of near field proximity transmitter device.

In an embodiment, the transaction process comprises a software modulewhich is arranged to make a connection between the customer apparatusand the financial institution application and provide the transactiondata to the financial institution application, and enable provision ofthe security device to the financial institution application.

In an embodiment, the reader and transaction processor may comprise asoftware application loaded onto mobile device hardware.

In an embodiment, the transaction data may comprise payment data. Thepayment data may comprise a payment amount, to be paid by the customerto a product provider. It may also include details of a product provideraccount that the financial institution can pay the payment amount into.

In an embodiment, the transaction data may comprise a reference code. Inthis embodiment, the reference code may be provided to the financialinstitution from the customer device and then from the financialinstitution to a transaction administrator system. The transactionadministrator system may receive payment data from the product provider,and provides the payment data to the financial institution in responseto the financial institution providing the reference data to thetransaction administration system.

Where there is a transaction administration system, the transactionadministration system may support the reader and transaction process.The reader and transaction process may be a software application(s)supported by the transaction administration system and provided to thecustomer for loading on to a customer device, such as a customer mobiledevice.

In an embodiment, the product provider artefact may be associated with aproduct being provided by the product provider. It may be a codeappearing on an actual product at point of sale so that the customer canpay for the product at point of sale using the customer apparatus. Itmay be a code appearing on a vending machine, so the product can bevended after the customer has paid for the product via their customerapparatus. It may be a code appearing on a computer screen, so that thecustomer can pay for an on-line transaction via a merchant website,utilising the customer apparatus. In embodiments, this has the advantagethat a customer can pay directly from a customer account, using a mobiledevice, without having to provide any private information to the productprovider, such as credit card details or other private information.

It also has the advantage of enabling a secure payment to be made eventhough a user may be using an untrusted or public computer to selectproducts from the merchant website. The product may be any good orservices.

In an embodiment, the financial institution application may be aninternet application, such as an internet banking application. In anembodiment, the internet banking application may allow access by thecustomer to their own account details, and enable them to pay directlyfrom their own account, as with conventional internet banking.

In accordance with a second aspect, the present invention provides atransaction administration apparatus, comprising a processing apparatus,and a product provider artefact providing module arranged to provide aproduct provider artefact including transaction data, to a productprovider apparatus, so that the product provider apparatus may providethe transaction data to a customer apparatus in accordance with thefirst aspect of the invention, so that the customer apparatus can obtainthe transaction data for facilitating payment for the transaction.

In an embodiment, the product provider artefact may be any code or datastored in any way that can be transmitted or presented to the customerapparatus.

In an embodiment, the transaction administration apparatus includes atransaction processing module, arranged to receive payment data from aproduct provider, and to provide the payment data to a financialinstitution application, so that the financial institution applicationcan deal with payment to the product provider from a customer account.

In an embodiment, the transaction administration apparatus includes areceipt module, arranged, on confirmation from a financial institutionapplication, to provide receipt data to a product provider apparatus,confirming that payment has been made to a product provider account tomeet payment for the transaction.

In an embodiment, the transaction administration apparatus comprises acomputing apparatus which is programmed with appropriate applications toimplement the production of the product provider artefact, handling oftransaction data between the financial institution apparatus and theadministration apparatus, and handling of payment data between theproduct provider apparatus and transaction administration apparatus andhandling and provision of receipt data to the product providerapparatus.

In accordance with a third aspect, the present invention provides aproduct provider artefact storing transaction data about a transactionbetween a customer and a product provider, and being readable by acustomer apparatus in accordance with the first aspect of the inventionin order for the customer apparatus to obtain the transaction data.

The product provider artefact may, in embodiments, be a code, such asQRcode, or may be a memory and transmitter for transmitting data fromthe memory, such as an RFID device or other transmitter arrangement.

In accordance with a fourth aspect, the present invention provides aproduct provider apparatus, comprising a processing apparatus arrangedto store a product provider artefact for transmission to a customerapparatus in accordance with the first aspect of the invention.

In accordance with a fifth aspect, the present invention provides acomputer program comprising instructions for controlling a computingdevice to implement a customer apparatus in accordance with the firstaspect of the invention.

In an embodiment, the computing device is a mobile communicationsdevice, such as a mobile telephone, for example.

In accordance with a sixth aspect, the present invention providescomputer readable medium, providing a computer program in accordancewith the fourth aspect of the invention.

In accordance with a seventh aspect, the present invention provides adata signal comprising a computer program in accordance with the fourthaspect of the invention.

In accordance with an eighth aspect, the present invention provides acomputer program comprising instructions for controlling a computer toimplement a transaction administration apparatus in accordance with thesecond aspect of the invention.

In accordance with a ninth aspect, the present invention provides acomputer readable medium, providing a computer program in accordancewith the seventh aspect of the invention.

In accordance with a tenth aspect, the present invention provides a datasignal, comprising a computer program in accordance with the seventhaspect of the invention.

In accordance with an eleventh aspect, the present invention provides atransaction processing system, comprising a transaction administrationapparatus in accordance with the second aspect of the invention and acustomer apparatus in accordance with the first aspect of the invention.

In an embodiment, the system further comprises a product providerartefact in accordance with the third aspect of the invention.

In an embodiment, the system further comprises a product providerapparatus in accordance with the fourth aspect of the invention.

In accordance with a twelfth aspect, the present invention provides asystem for facilitating transaction processing, comprising a customerapparatus in accordance with the first aspect of the invention and aproduct provider artefact in accordance with the third aspect of theinvention.

In accordance with a thirteenth aspect, the present invention provides amethod of facilitating payment transactions between a customer and aproduct provider, comprising the steps of using a customer apparatus toread a product provider artefact storing transaction data about thetransaction, to obtain the transaction data, connecting the customerapparatus over a communication network to a financial institutionapplication of a financial institution and providing the transactiondata to the financial institution application, so that the financialinstitution can make payment for the transaction from the customeraccount.

In an embodiment, the method includes the step of providing, via thecustomer apparatus, a security device to the financial institutionapplication to enable the transaction to proceed. The security devicemay comprise any security device, for example a password or biometric orany other security device.

In an embodiment, the customer apparatus is a mobile device. It may be amobile telephone, PDA, tablet computer, or any other mobile device whichcan transmit and receive information over a mobile telecommunicationsnetwork.

In accordance with a fourteenth aspect, the present invention provides amethod for facilitating a payment transaction between a customer and aproduct provider, the method comprising the steps of a financialinstitution computing system receiving transaction data about thetransaction from a customer apparatus, the customer apparatus havingread the transaction data from a product provider artefact storing thetransaction data, and making payment for the transaction from a customeraccount of the customer associated with the customer apparatus.

In an embodiment, the method comprises the step of receiving a securitydevice from the customer apparatus to enable the transaction to proceed.The security device may be a password, biometric or any other securitydevice.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparentfrom the following description of embodiments thereof, by way of exampleonly, with reference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating elements engaged in atransaction facilitating process in accordance with an embodiment of thepresent invention;

FIG. 2 is a block diagram of a customer apparatus in accordance with anembodiment of the present invention;

FIG. 3 is a flow diagram illustrating a transaction process implementedvia the elements of FIG. 1;

FIG. 4 is a schematic block diagram illustrating elements engaged in atransaction process in accordance with a further embodiment of thepresent invention;

FIG. 5 is a flow diagram illustrating the transaction process inaccordance with the further embodiment of the invention; and

FIGS. 6A through 6I are example screen shots illustrating operation of acustomer apparatus in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION OF EMBODIMENTS

An embodiment of the invention will now be described with reference toFIGS. 1 to 3.

FIG. 2 illustrates a customer apparatus, generally designated byreference numeral 1, for facilitating payment transactions between acustomer and a product provider. Customer apparatus 1 is also shown inFIG. 1.

FIG. 2 is a schematic block diagram of the components of the customerapparatus 1.

The customer apparatus 1 comprises a reader 2 and a transaction process3. In this embodiment, the reader 2 and transaction process 3 aresoftware modules forming a transaction processing application 4. Thereader 2 is arranged to obtain transaction processing data from aproduct provider artefact. In this embodiment, the product providerartefact may comprise a visible code 10 or transaction data stored in amemory for transmission 11 eg RFID tag, generated, encoded or spokenaudio tones, or keyed in manually.

The reader 2 is arranged to read the code or obtain the transaction datafrom the memory, via an appropriate hardware interface of the customerapparatus 1 (eg camera 20, wireless interface 21, microphone 27,keyboard 25).

The transaction process 3 is arranged to connect the customer apparatus1 to a financial institution application supported by a financialinstitution system 30. The financial institution system 30 may be anyappropriate computing apparatus and is illustrated in FIG. 1schematically as being one or more computer server apparatus 30. In thisembodiment, the financial institution (FI) system supports the financialinstitution application 31 which provides web pages 32 for access overthe Internet or other telecommunications systems 50 via the customerapparatus 1.

The transaction process connects to the FI application 31 and providesthe transaction data to the FI application 31.

In this embodiment the transaction data may include payment informationenabling an account of a product provider of a product to be paid by thefinancial institution system 30. In this embodiment, the financialinstitution administers an account of a customer associated with thecustomer apparatus 1. The product provider is paid from the customeraccount, when the customer authorises payment from the customerapparatus 1. Payment authorisation may be carried out over theconnection implemented by the transaction process 3, by providing asecurity device to the FI application 31. The security device may be aPIN, or other type of password, biometric, digital signature or anyother type of security device.

In more detail, the customer apparatus in this example comprises amobile device 1. The mobile device may be a mobile telephone, PDA,tablet computer, portable computer or any other type of mobile devicewith a communications facility. Example components for such a device areillustrated in FIG. 2. It will be appreciated that there are many suchdevices available.

Referring to FIG. 2, the customer mobile device comprises a processor 6for processing instructions which may be in the form of computersoftware. It also comprises a memory 7 for storing data andinstructions.

Note that the processor 6 may be any type of available processor and thememory 7 may include any type of memory, including ROM and RAM. Thememory stores the transaction application 4 which is implemented by theprocessor 6.

The mobile device 1 also includes a transceiver 22 for sending andreceiving voice and data communications over telecommunications network50. In addition it includes a wireless interface 21 for wirelesscommunications, such as WiFi, Bluetooth, or a wired interface where thedevice is connected to a computer or network device via a physicalconnection means.

The device 1 also includes a SIM card 23 display and display drivers 24,keyboard and keyboard drivers 25, speaker 26 and microphone 27.

Note that the layout shown in FIG. 2 is one potential architecture only.A customer apparatus having a functionality described herein may have adifferent architecture from this and may include additional or differentcomponents from that shown in FIG. 2. In addition, although in thisembodiment, the reader and transaction process are in the form of asoftware application 4 loaded onto the device 1, the invention is notlimited to this architecture. The application 4 may be either partly orfully in the form of hardware, eg firmware or PGAs or FPGAs, or anyother configuration.

The device 1 comprises a mobile device which can be used forconveniently dealing with payment transactions for products provided byproduct providers, such as merchants.

The customer apparatus 1 in accordance with this embodiment may be usedto pay for payment transactions for the purchase of products (any goodsor services) provided by a product provider.

The product provider may be any person or entity providing products(which may include any good and/or services) for sale (or hire or anyother type of transaction). In this embodiment, each product for sale isassociated with a product provider artefact 10, 11 (FIG. 1). The productprovider artefact 10, 11 is arranged to provide transaction data to thecustomer apparatus 1. It may be a visibly readable code, such as QRcode,barcode or any other visible code. It may also be stored in a memorydevice for transmission to customer apparatus 1 eg by wireless, WiFi,Bluetooth, sound tones or physical connection means. It may be an RFIDtag for example, associated with a product. As discussed above, thecustomer apparatus 1 is arranged to obtain the transaction data andutilise the transaction data to interface with a FI application 31 topay for the product from a customer account.

The transaction data may be associated in a number of ways with a numberof different types of product and product sales channels. FIG. 1 givessome examples:

-   -   products sold by way of vending devices 60 may be paid for using        this embodiment. QRcode, barcode or other code 10 is associated        with each product vended. As the product has been paid for via        the device 1 and FI system 30, and payment is acknowledged to a        product provider system 70, then the product provider system 70        may instruct the vending device 60 to release the product.    -   The product provider artefact may be associated with a parking        meter 61 for payment for parking services. When the product        provider system 70 receives acknowledgement of payment, it may        control the parking meter 61 to provide an indication (eg a        ticket) that the parking has been paid for.    -   The product may be associated with an RFID device 62 eg at point        of sale. Once the product has been paid for (and acknowledged to        system 70) then the product may be released.    -   The customer apparatus 1 may be used to purchase goods/services        which are provided on-line eg via the internet. A product        provider computing apparatus 70 (eg a merchant computer        providing an Internet shopping site) may be arranged to serve        web pages 63 over the communications network 50, for browsing by        customer apparatus 1. Web pages 63 may offer products for sale        which the customer may wish to purchase and pay for via their        customer apparatus 1. To facilitate payment, the system 70        generates code 10 on one of the web pages which includes the        transaction data, to enable the customer apparatus to deal with        the transaction. The product may then be provided when the        product provider system 70 receives acknowledgement of payment        from the FI system 30.

Embodiments of the invention are not limited to transactions forproducts associated with parking meters, online, vending devices, RFIDs,in store terminals (eg recharging of mobile phone credits), or cashregisters. Any product sales channel may be utilised, as long as thetransaction data can be provided to the customer apparatus 1.

In this embodiment, the FI application 31 is the usual internet bankingapplication provided by an FI for access by customers having accountsadministered by the FI. Such internet banking applications are wellknown.

The transaction process 3 is arranged to interface with the FIapplication 31 and fill in the appropriate details of eg productprovider account, amount to pay. The customer then controls theirapparatus to provide a password or other security device to thefinancial institution and designate which account they will pay from.This is similar to how standard internet banking applications areoperated, but in this case done via a mobile device and using thetransaction data provided by the product provider artefact.

In an embodiment, the transaction process may include an agentapplication which is arranged to automatically access the FI application31 and fill in the appropriate fields utilising the transaction data.That is, the customer does not have to control the apparatus, eg theapparatus keypad in order to enter the data. It is automatically enteredinto the FI application 31 by the transaction process.

In an embodiment, the transaction process may also be authorised toautomatically enter the security device of the customer. In analternative embodiment, the customer may be required to manually enterthe security device.

FIG. 3 is a flow diagram illustrating a transaction process inaccordance with this embodiment.

At step 101, the customer shops and selects their product. The customerthen uses their mobile device 1 to scan the transaction data (if it is acode) or obtain transaction data via wireless connection (if it isstored by RFID or equivalent technology), or by connecting the devicedirectly, or through the input of generated sound tones (102).

The transaction process 3 then causes a connection to the FI application31 and provides the transaction data to the FI application 31 (103). At104 payment details are obtained and entered into the FI application. Inthis embodiment this is done by the payment details being included inthe transaction data. The payment details include a payment amount anddetails of a product provider account, so that the FI system 30 can paythe product provider account. In another embodiment (see later) thetransaction data may comprise a reference which is used by the FI system30 to obtain payment details from elsewhere (see later).

At step 105, a security device, such as a PIN or password, is obtainedvia the customer mobile device. As discussed above, in somecircumstances this may automatically be provided by the transactionprocess 3.

At step 106, the FI pays the product provider from the customer account.At step 107 the FI provides an acknowledgement or receipt to the productprovider system 70.

FIGS. 4 and 5 illustrate a further embodiment of a transaction processwhich may be implemented in accordance with the present invention. FIG.4 is a schematic diagram similar to FIG. 2, with the addition of atransaction administration system 150. The transaction administrationsystem 150 allows a transaction administrator to take part in thesystem, and provide support and control to all transaction processesimplemented in accordance with this embodiment. The transactionadministration system 150 may be any computing device or system, of anyappropriate architecture. In this embodiment it is illustrated as beingone or more server systems having the appropriate software and hardwarefor providing the following functions and for transmitting and receivingdata via telecommunications networks 50. The other components of FIG. 4remain the same as FIG. 1 and use the same reference numerals.

The transaction administration system 150 in this embodiment has anumber of functions:

-   -   1. To provide support and updates for the transaction processing        application 4. The transaction administration system 150 may        make the transaction processing application 4 available over        communications network 50 for downloading by the customer        apparatus 1. It may also provide updates to the transaction        processing application 4. It may also make the transaction        application 4 available through third party distribution        channels eg an “Appstore”    -   2. The provision and maintenance of transaction data, in the        form of codes or data to store in memory of a wireless device        such as an RFID. In this embodiment, the transaction system 150        is arranged to receive payment information from a product        provider, such as identity of a product, payment amount required        and account of the product provider. It takes this payment        information and provides a product provider artefact, such as a        code or data for use in a wireless memory, and provides it back        to the product provider system 70 so that the product provider        system can provide it in association with its product(s) (eg via        web pages 63, parking meter 61, RFID 62, vending device 60 or in        any other way). This enables the system 150 to control the        transaction data and product provider and ensure that it is        compatible with the transaction processing application on the        customer apparatus 1. It also means that the system 150 can act        as central coordinator for all transactions, maintaining        consistency and quality of the transaction processing as well as        the security of product account information. The payment        information may be provided before the transaction or in real        time during the transaction.    -   3. The system 150 is arranged to communicate with the FI system        30 to provide payment information so that FI 30 can deal with        the payment.    -   4. The system 150 is arranged to receive acknowledgement that        payment has been made from the FI system 30 and provide        acknowledgement to product provider system 70 that payment has        been made. The system 150 may provide a receipt to product        provider system 70.    -   5. The system 150 also includes a database 151 which stores a        record of all transactions. The record can be accessed by        customers and also by product providers to obtain records of the        transactions made using the process of this embodiment of the        invention.

In this embodiment, the actual payment information that is received fromthe product provider system 70 may include information such as paymentamount, account to be paid (eg merchant account). It may also include aproduct identification, if required. Instead of encoding thisinformation, in one embodiment, the transaction administration system150 stores the payment information in database 151, and associates itwith a reference. For example, the reference may be a number, or numberand letters, or any other device. The reference is then encoded (orotherwise provided as a product provider artefact) and provided to theproduct provider system 70 for use with the associated product. Thetransaction data which is stored in the code 10 or memory 11 thereforeincludes a reference and does not include any payment information. Thishas the advantage that no private information of the product provider(eg account to be paid) is provided to any customer over the network. Itis only provided to the trusted transaction administration system 150.All the customer apparatus 1 obtains is a reference. Note that there maybe variations from this, and that the code may include a payment amountor other information, for example, but may not include the account to bepaid information. This protects the security of the product provider 70.

When the reference is provided by the customer apparatus 1 to thefinancial institution application 31, the financial institution 30 thencontacts the transaction administration system 150 and requests thestored payment information, using the reference. The transactionprocessing system 150 provides the payment information to the FI system30, so that the payment can be made.

FIG. 5 is a flow diagram which shows the transaction process of thisembodiment.

Steps 200 and 201 illustrate the process for the transactionadministration system 150 generating the product provider artefactincluding the transaction data. At 200, the transaction processingsystem 150 receives the payment information for a product from theproduct provider system 70. This may be done as a separate process. Forexample, when the product provider 70 decides to provide products forsale “on the shelf” they obtain a plurality of codes, one for each ofthe products, from the transaction administration system 150.Alternatively, the code may be generated at the time a customer wishesto purchase the product. That is a customer may indicate they wish topurchase a product, and then the product provider system 70 requests thetransaction administration system 150 for an appropriate code to beprovided to the customer.

At step 201, the transaction administration system 150 generates theproduct provider artefact (code or appropriate transaction data or otherartefact). As discussed above, this can be done prior to anytransactions, or in “real time” during the transaction.

Whether the product provider artefact is provided by the transactionadministration system in real time or in advance will depend upon thecircumstances and requirements of the product provider and transactionadministrator. Both options may be provided.

A transaction process of this embodiment is as follows.

At step 202, the customer shops and selects their product. At step 203,the customer mobile device 1 scans the code or obtains the transactiondata via wireless.

The transaction process 3 then connects to the FI application (204) andprovides the transaction data. In this embodiment, the transaction datais in the form of a reference, and does not include private information,such as the account details of the product provider, for example. Atstep 205, the financial institution system 30 connects with thetransaction administration 150 and requests payment data, such aspayment amount and account to pay to.

At step 206, these payment details are returned from the administrationsystem to the FI application 31, so FI application may utilise thesedetails for the current transaction. The FI application 31 may be theusual internet banking application provided by the FI. At step 207 thesecurity device is obtained via the customer mobile device 1, either bymanual entry of the customer or automatically being provided by thetransaction process 3.

The FI system 30 then pays the merchant account from the customeraccount, step 208. Payment may use existing mechanisms, e.g. “PayAnyone”, “Faster Payments”, “ACH” or any other mechanism.

At step 209, the FI system 30 provides a receipt to the transactionadministration system 150. The transaction administration system 150then provides the product provider system 70 with the receipt. Theproduct provider may then release the product. Note that in someembodiments the product may be released at another time. In some casesit may be released before the product provider receives confirmation ofpayment. The actual transfer of funds may be performed in real time orat a later time eg in an overnight batch bank process.

The transaction processing system 150 also enters details of thetransaction in the record 151, so it can subsequently be accessed by thecustomer and by the merchant.

In the above embodiment, the transaction data is provided by a productprovider artefact, which may be in the form of a visible code ortransaction data stored in a memory on a wireless device such as an RFIDtag. The invention is not limited to these methods of providing theartefact. The transaction data may be provided in other ways.

FIGS. 6A to I are screen shots illustrating how a mobile application inaccordance with an embodiment of the present invention may function on amobile device such as a Smartphone or tablet computer, for example.

FIG. 6A shows a “home screen” 500 including “App” icon 501 for a mobiletransaction processing application in accordance with an embodiment ofthe present invention. The icon is activated to activate the applicationif a customer wishes to make a mobile purchase, for example.

FIG. 6B shows an application screen 503 which indicates to the user thatthey should use the reader of the device to scan the QRcode tofacilitate the transaction.

The transaction application connects to the internet banking site of theuser and requires the user to enter their PIN code (screen 503, FIG.6C).

Referring to 6D, screen 504, the user is presented with a selection oftheir accounts which they may wish to pay for the transaction from.

FIG. 6E, screen 505 illustrates the transaction details being presentedto the customer. The customer can either cancel 506 or confirm 507 theirpurchase.

FIG. 6F, screen 508 shows how the transaction receipt details may bepresented to the user.

FIG. 6G, screen 509 illustrates how a record of purchases may bepresented to the user.

FIG. 6H, screen 510 illustrates transaction details that may bepresented to the user if they wish to inquire about the details oftransactions that have already taken place.

FIG. 6I, screen 511 illustrates a tool which enables a user to view abreakdown of types of purchases that they may have made via the system.Such a breakdown could be used for future budgeting purposes. In thisembodiment, the breakdown is shown in percentage terms of variouscategories such as “Dining Out”, “entertainment” and others. It will beappreciated that the calculations may be varied and the breakdown may beshown in otherwise than percentages.

Any names used in the drawings, such as “Payo”, it will be appreciatedour trademarks only and are not limiting to the present invention.

Another application of an embodiment of the present invention may be tofacilitate cash transactions at ATM's. There are a number of problems ofATM's “skimming” people's cards and PINs i.e. someone installs a deviceonto the ATM that reads the card and takes a video of the user enteringtheir PIN. They later create a fake card with the details and stealmoney from the victim's account.

In one embodiment, an ATM may be arranged to produce a QRcode or someother code that may be detected by a mobile device configured inaccordance with the present invention. The user can scan the code ontheir mobile device, login into or phone the bank to select an option todispense cash and then the ATM receives the message telling it torelease the cash. This provides an added layer of security to the ATMtransaction.

This kind of confirmation that a transaction should proceed, could beused with all types of transaction.

One of the advantages of this invention is that it can use standardalready existing financial institution applications, such as standardinternet banking applications. These applications in many cases, may notneed to be changed, or require relatively minormodifications/enhancements. The current fields of these applications aresufficient to enable payment information to be filled into them, usingthe processes and apparatus of the present invention.

In the above embodiment, where the transaction administration system 150communicates with the FI system 30 and the product provider system 70,the transaction administration system 150 may establish securecommunications with either one or both of these systems for transport ofsecure data, such as account details and the like.

Another way in which the code could be provided to a customer could beas an image on a transaction record, such as a bill for payment. Itcould arrive through the post or via email, and then the customerapparatus would utilise the code to pay for the bill.

In the above embodiment, the customer apparatus 1 is a mobile device.Although this is the preferred embodiment, in other embodiments thecustomer apparatus may be stationary. For example it may be a PC with ascanner. The scanner could be used particularly for embodiments inreading codes from bills for payment eg electricity bills and the like.

Various parts of embodiments of the invention may be implemented bycomputer programs, which may be provided as program code. The programcode could be supplied in a number of ways, for example on a tangiblecomputer readable storage medium, such as a disk or a memory, or as adata signal (for example combine transmitting it from a server). Theprogram code provides a series of instructions executable by aprocessor, such as the processor of the customer apparatus 1.

Note that in other embodiments the program may be in the form ofhardware, or firmware, such as in the form of FPGAs or PGAs.

In the claims which follow and in the preceding description of theinvention, except where the context requires otherwise due to expresslanguage or necessary implication, the word “comprise” or variationssuch as “comprises” or “comprising” is used in an inclusive sense, i.e.to specify the presence of the stated features but not to preclude thepresence or addition of further features in various embodiments of theinvention.

It will be understood to persons skilled in the art of the inventionthat many modifications may be made without departing from the spiritand scope of the invention.

1. A customer apparatus for facilitating payment transactions between acustomer and a product provider, the customer apparatus comprising: areader arranged to read a product provider artefact storing transactiondata about the transaction, to obtain the transaction data; and atransaction processor arranged to connect over a communication networkto a financial institution application of a financial institutionadministering a customer account of the customer, to provide thetransaction data to the financial institution application, so that thefinancial institution can make payment for the transaction from thecustomer account.
 2. An apparatus in accordance with claim 1, thecustomer apparatus comprising a mobile device.
 3. An apparatus inaccordance with claim 1, wherein the product provider artefact is avisible code.
 4. An apparatus in accordance with claim 1, wherein theproduct provider artefact comprises a memory for storing the transactiondata for transmission to the customer apparatus.
 5. An apparatus inaccordance with claim 1, wherein the transaction data comprises apayment amount and details of a product provider account, wherein thefinancial institution can pay the payment amount into the productprovider account.
 6. An apparatus in accordance with claim 1, whereinthe transaction data comprises a reference, arranged to be received bythe financial institution and provided to a transaction administrationsystem, the transaction administration system being arranged to providepayment data to the financial institution in response to receipt of thereference.
 7. An apparatus in accordance with claim 1, wherein thefinancial institution application is a conventional Internet bankingapplication.
 8. A transaction administration apparatus comprising: aprocessing apparatus; and a product provider artefact providing modulearranged to provide a product provider artefact including transactiondata, to a product provider apparatus, so that the product providerapparatus may provide the transaction data to a customer apparatus inaccordance with the first aspect of the invention, so that the customerapparatus can obtain the transaction data for facilitating payment forthe transaction.
 9. An apparatus in accordance with claim 8, comprisinga transaction processing module arranged to receive payment data from aproduct provider, and to provide the payment data to a financialinstitution application, so that the financial institution applicationcan deal with payment to the product provider from a customer account.10. A product provider artefact storing transaction data about atransaction between a customer and a product provider, and beingreadable by a customer apparatus in order for the customer apparatus toobtain the transaction data.
 11. A non-transitory computer-readablemedium having stored therein a computer program comprising instructionsfor controlling a computing device to implement a customer apparatus inaccordance with claim
 1. 12. A transaction administration systemcomprising a transaction administration apparatus in accordance withclaim 8, and a customer apparatus for facilitating payment transactionsbetween a customer and a product provider, the customer apparatuscomprising: a reader arranged to read a product provider artefactstoring transaction data about the transaction, to obtain thetransaction data; and a transaction processor arranged to connect over acommunication network to a financial institution application of afinancial institution administering a customer account of the customer,to provide the transaction data to the financial institutionapplication, so that the financial institution can make payment for thetransaction from the customer account.
 13. A system, in accordance withclaim 12, further comprising a product provider artefact storingtransaction data about a transaction between a customer and a productprovider, and being readable by a customer apparatus in order for thecustomer apparatus to obtain the transaction data.
 14. A method offacilitating payment transactions between a customer and a productprovider, the method comprising: using a customer apparatus to read aproduct provider artefact storing transaction data about thetransaction, to obtain the transaction data; and connecting the customerapparatus over a communication network to a financial institutionapplication of a financial institution and providing the transactiondata to the financial institution application, so that the financialinstitution can make payment for the transaction from the customeraccount.
 15. A method for facilitating a payment transaction between acustomer and a product provider, the method comprising: read, at acustomer apparatus, transaction data about the transaction from aproduct provider artefact storing the transaction data; receiving, at afinancial institution computing system, the transaction data from thecustomer apparatus; and making payment for the transaction from acustomer account of the customer associated with the customer apparatus.